As Shipa evolves, to leverage newer APIs, providers will need to be upgraded. The chart below is the minimum version of the provider for each version of Shipa.

IaC Provider	Shipa 1.6.2	Shipa 1.6.3	Shipa 1.7.0+/Cloud
Terraform	0.0.6	0.0.7	0.0.11
Crossplane	0.0.1	0.0.3	0.0.5
GitHub Actions	0.0.1	0.0.1	0.0.1

Terraform Upgrades

To upgrade your Terraform Provider, change the required provider version and rerun Terraform Init.

#Terraform Version
terraform {
  required_providers {
    shipa = {
      version = "0.0.13"
      source = "shipa-corp/shipa"
    }
  }
}

#Terraform Init
terraform init -upgrade

Crossplane Upgrades

To upgrade your Crossplane Provider, change the spec package to a later version of the Shipa Provider and re-apply in your clusters.

#crossplane-provider-shipa
apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
  name: provider-shipa
spec:
  package: "shipasoftware/provider-shipa:0.0.5"
  
#apply
kubectl apply -f crossplane-provider-shipa.yaml

GitHub Actions Upgrades

Change the Shipa GitHub Actions dependencies in your Actions configuration(s). Depending on your trigger you might have to commit/make a change to pick up on the latest version. E.g the uses line.

jobs:
  create_policies:
    runs-on: ubuntu-latest
    name: Create Policy Frameworks
    steps:
      - name: Checkout
        uses: actions/[email protected]
      - name: Creating Framework
        uses: shipa-corp/[email protected]
        env:
          SHIPA_TOKEN: ${{ secrets.SHIPA_TOKEN }}
          SHIPA_HOST: ${{ secrets.SHIPA_HOST }}
        with:
          shipa-action: './infra/fw-policies.yml'