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.

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

Skip disabling AWS Exocompute for non-CFT workflow #172

Merged
merged 2 commits into from
May 28, 2024

Conversation

johan3141592
Copy link
Member

No description provided.

@johan3141592 johan3141592 requested a review from a team as a code owner May 28, 2024 12:11
@johan3141592 johan3141592 merged commit 904300f into beta May 28, 2024
2 checks passed
@johan3141592 johan3141592 deleted the skip-disabling-exocompute-for-noncft branch May 28, 2024 15:24
johan3141592 added a commit that referenced this pull request Aug 5, 2024
* Add support specifying Azure resource groups for RSC features (#160)
* Add retry to allVpcsByRegion request (#162)
* Move the retry handling into the Request function (#165)
* Expose account name and FQDN (#166)
* Add support for Azure shared exocompute (#167)
* Fix an issue with AWS exocompute customer supplied security groups (#168)
* Add support for Azure archival locations (#169)
* Fix Azure permission upgrade issue (#170)
* Increase the korg job wait attempts to 50 (#171)
* Skip disabling AWS Exocompute for non-CFT workflow (#172)
* Fix CreateStorageSetting's NativeID field (#173)
* Use RSC_MANAGED_CLUSTER permission group (#174)
* Extend AddClusterToExocomputeConfig to return setup YAML (#175)
* Disable S3 protection before removing the feature (#176)
* Fix failing Azure integration tests (#177)
* Work around an AWS multiple features removal issue (#178)
* Add functions to look up cloud accounts by native ID and name (#180)
* Add support for updating AWS archival location bucket tags (#179)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants