DATAGO-121329: Explicitly use vault token for reading SolaceDev packages

[AmanRiat1]

• The default github token does not have access to maven packages in SolaceDev as that is what was being used before
• Now we use the readonly token to get the maven packages in SolaceDev but use the default github workflow token to publish to github packages

[shooshmand-sol]

wondering can this token deploy to github packages (this looks readonly?) , or it is just for reading, and write is done using github_token?

[AmanRiat1]

yes exactly that

[AmanRiat1]

Basically the packages token works for this in the settings.xml to get packages from SolaceDev

  maven/settings.xml (lines 37-41):
  <server>
      <id>github-solacedev</id>
      <username>${env.PACKAGES_READ_USER}</username>
      <password>${env.PACKAGES_READ_TOKEN}</password>
  </server>

  This matches the repository definition at lines 20-31:
  <repository>
      <id>github-solacedev</id>
      <url>https://maven.pkg.github.com/SolaceDev/*</url>
      ...
  </repository>

When we publish we use this profile which use the github workflow token to publish the package:

  maven/settings.xml (lines 42-46):
  <server>
      <id>github</id>
      <username>${env.GITHUB_ACTOR}</username>
      <password>${env.GITHUB_TOKEN}</password>
  </server>

  pom.xml (lines 641-647) - In the profile activated by -DreleaseTarget=github:
  <distributionManagement>
      <repository>
          <id>github</id>
          <name>GitHub SolaceProducts Maven Packages - Binder</name>
          <url>https://maven.pkg.github.com/SolaceProducts/pubsubplus-connector-spark</url>
      </repository>
  </distributionManagement>

[shooshmand-sol]

Awesome, thanks for explanations @AmanRiat1