Update workflows for external sub clusters. #211
Merged
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
This commit updates the workflows to use the clusters configured in the OSS subscription. Those clusters were created as documented in dapr#167. Those clusters live in distinct subscription and have distinct names as the current ones -- hence the need to update the workflows. Additionally, because those clusters use Bicep-configure Azure-hosted state store, binding and pubsub components, there is no need to configure Redis, Kafka or setup individual components. Signed-off-by: Tiago Alves Macambira <[email protected]>
tmacam
force-pushed
the
UpdateWorkflowsForExternSubClusters
branch
from
be5e582 to
629cba8
Compare
tmacam
commented
Nov 2, 2023
berndverst
approved these changes
Nov 6, 2023
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.
This commit updates the workflows to use the clusters configured
in the OSS subscription. Those clusters were created as documented
in #167.
Those clusters live in distinct subscription and have distinct names
from the current ones -- hence the need to update the workflows.
Additionally, because those clusters use Bicep-configure Azure-hosted
state store, binding and pubsub components, there is no need to
configure Redis, Kafka or setup individual components.
Signed-off-by: Tiago Alves Macambira [email protected]
Description
Please explain the changes you've made
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #[issue number]
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list: