Skip to content
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.

Sign up for GitHub

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

Jump to bottom

new service connection #3757

Merged
merged 4 commits into from
Mar 19, 2024
Merged

new service connection #3757

merged 4 commits into from
Mar 19, 2024

Conversation

rajithaalurims
Copy link
Contributor

@rajithaalurims rajithaalurims commented Mar 15, 2024 •
edited
Loading

Description

CI and PR pipelines started failing after rotating secret for service principal ADO is using.
This PR has changes to use new Service connection created.

Related issues

Addresses [issue 117888].

Testing

PR Build and Deploy

FHIR Team Checklist

  • Update the title of the PR to be succinct and less than 65 characters
  • Add a milestone to the PR for the sprint that it is merged (i.e. add S47)
  • Tag the PR with the type of update: Bug, Build, Dependencies, Enhancement, New-Feature or Documentation
  • Tag the PR with Open source, Azure API for FHIR (CosmosDB or common code) or Azure Healthcare APIs (SQL or common code) to specify where this change is intended to be released.
  • Tag the PR with Schema Version backward compatible or Schema Version backward incompatible or Schema Version unchanged if this adds or updates Sql script which is/is not backward compatible with the code.
  • CI is green before merge Build Status
  • Review squash-merge requirements

Semver Change (docs)

Patch|Skip|Feature|Breaking (reason)

@rajithaalurims rajithaalurims requested a review from a team as a code owner March 15, 2024 17:39
@rajithaalurims
Copy link
Contributor Author

/azp run

@azure-pipelines Azure Pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@rajithaalurims rajithaalurims added Azure API for FHIR Label denotes that the issue or PR is relevant to the Azure API for FHIR Azure Healthcare APIs Label denotes that the issue or PR is relevant to the FHIR service in the Azure Healthcare APIs labels Mar 19, 2024
@rajithaalurims rajithaalurims added this to the S137 milestone Mar 19, 2024
mikaelweave
mikaelweave approved these changes Mar 19, 2024
View reviewed changes
Copy link
Contributor

@mikaelweave mikaelweave left a comment

Choose a reason for hiding this comment

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

🦾

@LTA-Thinking LTA-Thinking merged commit 9e848c5 into main Mar 19, 2024
34 of 44 checks passed
@LTA-Thinking LTA-Thinking deleted the personal/rajitha/service-connection-testing branch March 19, 2024 21:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@fhibf fhibf fhibf approved these changes

@mikaelweave mikaelweave mikaelweave approved these changes

Assignees
No one assigned
Labels
Azure API for FHIR Label denotes that the issue or PR is relevant to the Azure API for FHIR Azure Healthcare APIs Label denotes that the issue or PR is relevant to the FHIR service in the Azure Healthcare APIs
Projects
None yet
Milestone
S137
Development

Successfully merging this pull request may close these issues.
4 participants
@rajithaalurims @mikaelweave @fhibf @LTA-Thinking