Added missing 'container' property in metadata on a package version.

[thomaslem]

Resolves #2683

The class was already there. It was just not being used in PackageVersionMetadata.

From looking at the API it looks like only adding the the property to the model should work.

Example API response with a tag:

"metadata": {
  "package_type": "container",
  "container": {
    "tags": [
      "develop"
    ]
  }
}

Example API response without a tag:

"metadata": {
  "package_type": "container",
  "container": {
    "tags": []
  }
}

Example API response for other package type:

"metadata": {
  "package_type": "npm"
}

---

Behavior

Before the change?

• No Container property is present on PackageVersionMetadata

After the change?

• A Container property is present on PackageVersionMetadata

Other information

• N/A

---

Additional info

Pull request checklist

• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)
• Added the appropriate label for the given change

Does this introduce a breaking change?

Please see our docs on breaking changes to help!

• Yes (Please add the Type: Breaking change label)
• No

If Yes, what's the impact:

• N/A

Pull request type

Please add the corresponding label for change this PR introduces:

• Bugfix: Type: Bug
• Feature/model/API additions: Type: Feature
• Updates to docs or samples: Type: Documentation
• Dependencies/code cleanup: Type: Maintenance

---

[thomaslem]

It looks like I can't add a label. Would be: Type: Feature

[thomaslem]

Looked at the docs and did not see anything related to PackageVersion to update. I build the package locally and tested if I got tags on containers and I did. I don't see any existing unit/integration tests for checking if data is on a PackageVersion response. If you want me to add tests could you point me in the right direction?

[kfcampbell]

Thanks! You're correct that there's not an existing way to test this but I'd rather get this in than hold it up on introducing new testing at the moment.