* Initial start of RP int automation
Creating new pipeline with new templates for some of the steps
* Rename files and fetch image tags for ACR images
Remove the int/integration phrase from file names and directories, add bash script for fetching the image tag from pkg/util/version/const.go, and remove the clenup subscription template
* Get default image, tag and import it to ACR
Add new functions and scripts to get the images tag and set it nicely for importing and copying images by digest (e.g., for the fluenbit image).
* Add validation commands for downloading secrets and rp-dev-config creation
Check created directory and three config files after downloading the secrets from the shared RP config, and validate that a new rp-dev-config file has been created
* Use Azure unique prefix
Use an Azure unique prefix for the Azure resource names that ARO-RP is creating
* Update env vars
No cahce is needed for running the pipeline, az aro source can be discarded, and remove the e2e suite var
* Simplify two bash scripts and use newer base image
Use UBI8 toolbox image v8.10 with a better name, and shorter env declartion or env validation over multiple lines
* Logically group steps for rp-full-dev-setup
Simplify 'main' pipeline by grouping them by their purpose and use -e flag for the bash scripts
* Typo fix + git commit
s/delpoy/deploy
* go.mod: Add github.com/microsoftgraph/msgraph-sdk-go
* azureclient: Add NewGraphServiceClient
Creates a GraphServiceClient with scope and graph endpoint set
appropriately for the cloud environment (public or US government).
* pkg/util/graph: Add GetServicePrincipalIDByAppID
* armhelper: Use MS Graph to obtain service principal ID
* armhelper: Remove unused authorizer parameter
* Use MS Graph endpoint to validate service principal
I don't think it matters for the purpose of validation, but the
AD Graph endpoint is nearing its end-of-life.
* pkg/cluster: Use MS Graph to obtain service principal ID
* pkg/util/cluster: Use MS Graph to create and delete clusters
* Pretty-print OData errors from MS Graph
To aid debugging failed MS Graph requests.
MS Graph's top-level APIError message is hard-coded and only says
"error status code received from the API". Further details have
to be extracted from the "ODataErrorable" interface type.
* azureclient: Remove ActiveDirectoryGraphScope
No longer used.
* Remove pkg/util/azureclient/graphrbac
No longer used.
* pipelines: Run CodeQL analysis for Go on 1ES Hosted Pool
Vendoring the Microsoft Graph SDK for Go causes memory consumption
during CodeQL analysis to double due to its enormous API surface,
putting it well beyond the memory limit of standard GitHub Action
runners.
I inquired with the Azure organization admins about provisioning
larger GitHub runners, but was directed instead to use the 1ES
Hosted Pool which runs our other CI checks. Since ARO controls
the VM type for Hosted Pool agents, we can use a VM type with
adequate memory for CodeQL analysis with the Graph SDK.
Note: Implemented CodeQL commands in a template in case we
ever decide to move Javascript or Python analysis to
1ES Hosted Pool as well.
Revert "Add name length validation on ARO clusters for non-zonal regions"
This reverts commit 13c3290ffc.
Revert "Typo in pipeline script"
This reverts commit 6e1acd4f13.
Revert "Truncate cluster names to 19 char in e2e pipelines"
This reverts commit b2273bdc6a.
Removed test cases in pkg/api/v20220904/openshiftcluster_validatestatic_test.go for cluster
name length validation, these tests are no longer needed as BZ 2093044 is fixed in 4.10.20
ARO uses both tags and commits as its version.
The commits are used for the development scenario,
tags are used when building and deploing to
production.
When annotated TAG is not set the new step fails.
Otherwise it builds the tagged image and pushes it
to the ACR.
Signed-off-by: Petr Kotas <pkotas@redhat.com>