ci; change to relative reference for reusable workflow to avoid havin… #4

	name: Build on push

	on:
	push:
	branches:
	- develop

	jobs:
	build-and-push:
	name: API Build and push develop to staging ECR
	uses: ./.github/workflows/build-push-to-ecr.yml
	with:
	path: api
	image-name: ausseabed-staging-sct-api
	aws-region: ap-southeast-2
	aws-account-id: 288871573946
	AWS_ACCESS_KEY_ID: ${{ secrets.STAGING_ACCESS_KEY_ID }}
Check failure on line 17 in .github/workflows/build-on-push.yml View workflow run for this annotation GitHub Actions / Build on push Invalid workflow file `The workflow is not valid. .github/workflows/build-on-push.yml (Line: 17, Col: 26): Unrecognized named-value: 'secrets'. Located at position 1 within expression: secrets.STAGING_ACCESS_KEY_ID .github/workflows/build-on-push.yml (Line: 18, Col: 30): Unrecognized named-value: 'secrets'. Located at position 1 within expression: secrets.STAGING_SECRET_ACCESS_KEY` Check failure on line 17 in .github/workflows/build-on-push.yml View workflow run for this annotation GitHub Actions / Build on push Invalid workflow file `The workflow is not valid. .github/workflows/build-on-push.yml (Line: 17, Col: 26): Unrecognized named-value: 'secrets'. Located at position 1 within expression: secrets.STAGING_ACCESS_KEY_ID .github/workflows/build-on-push.yml (Line: 18, Col: 30): Unrecognized named-value: 'secrets'. Located at position 1 within expression: secrets.STAGING_SECRET_ACCESS_KEY`
	AWS_SECRET_ACCESS_KEY: ${{ secrets.STAGING_SECRET_ACCESS_KEY }}

Provide feedback