Skip to content

[App Config] Migrate to core-v2#20766

Merged
HarshaNalluru merged 83 commits intoAzure:mainfrom
HarshaNalluru:harshan/app-config/15809
Apr 7, 2022
Merged

[App Config] Migrate to core-v2#20766
HarshaNalluru merged 83 commits intoAzure:mainfrom
HarshaNalluru:harshan/app-config/15809

Conversation

@HarshaNalluru
Copy link
Copy Markdown
Contributor

@HarshaNalluru HarshaNalluru commented Mar 10, 2022

Packages impacted by this PR

  • @azure/app-configuration

Issues associated with this PR

Fixes #6484 with #20817
Fixes #15809

Describe the problem that is addressed by this PR

Migrating app-config to core-v2

Command used to generate this PR:**(Applicable only to SDK release request PRs)

Generated code with generate:client script to get new core-v2 support.

Checklists

  • Added impacted package name to the issue description
  • Added a changelog (if necessary)

@ghost ghost added Azure.Core App Configuration Azure.ApplicationModel.Configuration labels Mar 10, 2022
@azure-sdk
Copy link
Copy Markdown
Collaborator

API changes have been detected in @azure/app-configuration. You can review API changes here

@check-enforcer
Copy link
Copy Markdown

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

What if I am onboarding a new service?

Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment:
/azp run prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run js - [service] - ci

@HarshaNalluru HarshaNalluru changed the title Harshan/app config/15809 [App Config] Migrate to core-v2 Mar 12, 2022
Copy link
Copy Markdown
Contributor

@sarangan12 sarangan12 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@HarshaNalluru Can you tell where you are getting the CompatResponse from?

Copy link
Copy Markdown
Contributor

@sarangan12 sarangan12 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After offline discussion with Harsha, LGTM

Copy link
Copy Markdown
Member

@jeremymeng jeremymeng left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. just one nit comment

);
return webResource;
}
export function createAppConfigKeyCredentialPolicy(
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: just appConfigKeyCredentialPolicy()

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

Copy link
Copy Markdown
Member

@xirzec xirzec left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes look good! Thanks for the updates, left some final thoughts. 👍

result: T
): asserts result is T & HttpResponseField<any> {
if (!hasUnderscoreResponse(result)) {
throw new Error(
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if we should instead log this (and maybe have it fail our tests as well) -- basically I would be a little concerned about breaking someone's usage of app-config if they don't rely on _response. Maybe if it doesn't exist we can attach a message on _response that says to file a bug? :)

We can take this as a follow-up issue, though

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh that's a great point.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

image
This good?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Works for me!

Comment thread sdk/appconfiguration/app-configuration/src/internal/synctokenpolicy.ts Outdated
Comment thread sdk/appconfiguration/app-configuration/src/internal/helpers.ts Outdated

if (hasUnderscoreResponse(kvp)) {
Object.defineProperty(response, "_response", {
enumerable: false,
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not technically required (all flags default to false), but I'm fine with making it explicit

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TIL

Comment thread sdk/appconfiguration/app-configuration/src/appConfigCredential.ts Outdated
}
}

export function toWebResourceLike(request: PipelineRequest): WebResourceLike {
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need full copies of all this compat code as test helpers? what are we validating?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was lazy. Removed everything and simplified.
Tests are happy, I'm happy.

@HarshaNalluru HarshaNalluru enabled auto-merge (squash) April 7, 2022 19:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

App Configuration Azure.ApplicationModel.Configuration Azure.Core

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[App Config]Move the App Config package to use core-rest-pipeline [core] Unify the ThrottlingRetryPolicy in core and app-configuration

7 participants