Please describe the feature/suggestion
Currently you cannot just type in two packages in the bundlephobia search bar and compare them.

Describe the solution you'd like
I think it would be muuuuch more user-friendly if any visitor of the website could write ANY of these:

• marked markdown-it or
• marked vs markdown-it or
• marked, markdown-it or
• marked || markdown-it

We should make the parameter ice.billing_s3bucketregion optionnal, as it is only required for region with v4 authentication.

Moreover this will make v1.1.2 backward compatible.

Issue type

• Bug Report

Build number

master branch

Configuration

Deployed as a Stack Set, with a CloudWatch Rule triggering the function

Summary

Can't confirm completely, but I believe the logger which is created from main.go 's setupLogging function does not get created, and therefore

The "Tag" section on each guide can encourage use of them for better asset management.
In this case (running labs) we can use them to mark resources created during the lab and tear them down later more quickly.

User Story

When the Azure provider was implemented, there were new JSONFields created in our models to store authentication and data source information.

The AWS and OCP providers are still using the AWS-specific model fields and should be migrated to using the new JSONFields and the old fields should be removed from the DB.

Impacts

API, UI

Role

Assumptions

API Details

| A

Summary

This request has a markup from New Relic's UI writer with copy changes to match New Relic's UI style guidelines and improve readability and usability.

Desired Behaviour

Markup document (internal access only): https://docs.google.com/document/d/10dWqR0vPF6q0r9UYhziW4xyHWdlVlZYBrUAX-KMG0a4/edit?u

When I choose the country with "China" or "Japan", printed image looks like wrong.
Please have a look at the following screenshots.

![screenshot_4](ht

Hi there,
I saw on the bottom of your marketplace entry the following line

Developing and testing extensions for VSTS is challenging, because the provided documentation is incomplete and not 100% up-to-date

I work on the VSTS team and we are committed to making the documentation and integration better. Would you please detail what information was wrong and what you felt was missing so we ca