provider-aws

Instructions for infoblox releases

The packages build from this repo are released on GitHub Package Manager (ghcr.io/infobloxopen/provider-aws).

The steps to build a new release for upgrading crossplane:

1. Setup this in local.

   $ git clone --recursive [email protected]:infobloxopen/provider-aws.git
   $ cd provider-aws
   $ git remote add upstream [email protected]:crossplane-contrib/provider-aws.git

2. Now fetch the release branch from upstream and checkout to that branch. Now using this as a base branch we will create our patch branch. The convention should be that patch branch should have suffix -ib. Eg.

   $ git fetch upstream release-0.43
   $ git checkout release-0.43
   $ git branch --set-upstream-to=origin/release-0.43
   $ git push origin release-0.43
   $ git checkout -b release-0.43-ib

3. On this branch we can add our CI changes to allow us to build the package and publish it to ghcr.io/infobloxopen/provider-aws. The changes required in .github/workflows actions are in commit: fc51fa5. To apply these changes to your branch we can simply cherry-pick this commit onto current branch.

   $ git cherry-pick fc51fa5
   $ git push origin release-0.43-ib

4. Now we can work on adding our custom changes as per change log and upstream as per requirement.
5. Once all changes are pushed to origin/<release-branch>-ib, we can build the package with github action ci.yaml of this branch. The CI action expects a version for package to build and publish. Convention is to keep it in semver format of vx.x.x-ib. This publishes the package to ghcr.
6. Now we can open a DCPR with this version specified in crossplane-provider-values.yaml in the key .Values.package.version.

Infoblox change log

1. update rds/dbinstance to update tags if modified

Overview

This provider-aws repository is the Crossplane infrastructure provider for Amazon Web Services (AWS). The provider that is built from the source code in this repository can be installed into a Crossplane control plane and adds the following new functionality:

• Custom Resource Definitions (CRDs) that model AWS infrastructure and services (e.g. Amazon Relational Database Service (RDS), EKS clusters, etc.)
• Controllers to provision these resources in AWS based on the users desired state captured in CRDs they create
• Implementations of Crossplane's portable resource abstractions, enabling AWS resources to fulfill a user's general need for cloud services

Getting Started and Documentation

For getting started guides, installation, deployment, and administration, see our Documentation.

Contributing

provider-aws is a community driven project and we welcome contributions. See the Crossplane Contributing guidelines to get started.

Adding New Resource

We use AWS Go code generation pipeline to generate new controllers. See Code Generation Guide to add a new resource.

Releases

AWS Provider is released every 4 weeks and we issue patch releases as necessary. For example, v0.20.0 is released on October 19, 2021. The next minor release v0.21.0 will be cut on November 16, 2021, and so on.

Report a Bug

For filing bugs, suggesting improvements, or requesting new features, please open an issue.

Contact

Please use the following to reach members of the community:

• Slack: Join our slack channel
• Forums: crossplane-dev
• Twitter: @crossplane_io
• Email: [email protected]

Roadmap

provider-aws goals and milestones are currently tracked in the Crossplane repository. More information can be found in ROADMAP.md.

Governance and Owners

provider-aws is run according to the same Governance and Ownership structure as the core Crossplane project.

Code of Conduct

provider-aws adheres to the same Code of Conduct as the core Crossplane project.

Licensing

provider-aws is under the Apache 2.0 license.