👷Publish `aries-cloudagent-bbs` Docker image

[rblaine95]

• Resolves #3174
• Adds dedicated Docker Metadata step for the BBS enabled docker image
• Prevents the Extended (BBS enabled) image from overwriting the non-BBS image

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[rblaine95]

@jamshale I should have caught it in #3171, thank you for being so quick to review 🙌

[jamshale]

Will merge after integration tests.

[swcurran]

So what is the impact of this going on after 1.0.0? Any concerns?

[jamshale]

I don't have any concerns. Doesn't affect any of the source code. We'll want to make sure the image is correct if it has been overridden by the bbs currently.

[jamshale]

That might involve deleting the current image and re-running the workflow. I'm not exactly sure.

[rblaine95]

@jamshale running the workflow manually and specifying the tag as 1.0.0 will overwrite the existing 1.0.0 image without having to do another release

[jamshale]

Going to do that now.

[rblaine95]

Ah, that 403 error, I've seen that happen if it's the first time a package is being pushed. Rerunning the workflow should resolve it.

[jamshale]

I've seen that too. Didn't know re-running it worked.

[rblaine95]

We (DIDx) had it happen a few times, especially when creating a large number of new packages in a single workflow run.

I think it's a hiccough with the Github API trying to provision new packages... some inconsistent backend state, something async that took just a little too long after creating the new package but before the permissions were configured in time 🤷

[jamshale]

Looks like it's published now :+1: