-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(vscode): Auto regenerate managed api connection keys #5147
Merged
ccastrotrejo
merged 14 commits into
ccastrotrejo/ConnectionsJoaquim
from
jmalcampo/connectionKey-regen
Jul 18, 2024
Merged
feat(vscode): Auto regenerate managed api connection keys #5147
ccastrotrejo
merged 14 commits into
ccastrotrejo/ConnectionsJoaquim
from
jmalcampo/connectionKey-regen
Jul 18, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… tests and logging
ccastrotrejo
changed the title
Jmalcampo/connection key regen
feat(vscode): Auto regenerate managed api connection keys
Jul 18, 2024
ccastrotrejo
approved these changes
Jul 18, 2024
ccastrotrejo
merged commit Jul 18, 2024
3f070c0
into
ccastrotrejo/ConnectionsJoaquim
9 of 14 checks passed
ccastrotrejo
added a commit
that referenced
this pull request
Jul 19, 2024
* introducing connectionKeys.ts for auto regenerate keys * removed comment in pickFuncProcess * jwtHelper compatible without atob and local setting file access fixes * add logic for resolving connection ids * added function to format settings before api call * updated jwtHelper and workflow services and their imports, added unit tests and logging * update changes to connection.ts * changed workflow to export functions and enabled duration telemetry * fixed typo in workflow * fixed workflow utility * feat(vscode): Auto regenerate managed api connection keys (#5147) * introducing connectionKeys.ts for auto regenerate keys * removed comment in pickFuncProcess * jwtHelper compatible without atob and local setting file access fixes * add logic for resolving connection ids * added function to format settings before api call * updated jwtHelper and workflow services and their imports, added unit tests and logging * update changes to connection.ts * changed workflow to export functions and enabled duration telemetry * fixed typo in workflow * fixed workflow utility --------- Co-authored-by: Joaquim Malcampo <jmalcampo@microsoft.com> * Solve issue with mocking libraries * adjusted unit tests and telemetry settings in pickFuncProcess --------- Co-authored-by: Joaquim Malcampo <jmalcampo@microsoft.com> Co-authored-by: Carlos Emiliano Castro Trejo <ccastrotrejo@microsoft.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Please Include Screenshots or Videos of the intended change: