TA-4668: Update documentation for get one version metadata command

[Buqeta (Buqeta)]

Description

After adding the LATEST keyword to the version path variable of the find one version endpoint, created this PR to update the documentation of the CLI command that uses that endpoint.

Relevant links

• Jira: https://celonis.atlassian.net/browse/TA-4668

Checklist

• I have self-reviewed this PR
• I have tested the change and proved that it works in different scenarios
• I have updated docs if needed

[Laberion Ajvazi (LaberionAjvazi)]

Should we also update the Documentation.md file?

[Buqeta (Buqeta)]

Should we also update the Documentation.md file?

Updated it.

[sonarqubecloud]

Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud

[Jeta (jetakasabaqi)]

I would merge this only after the API change is released.

[Zgjim Haziri (ZgjimHaziri)]

I would merge this only after the API change is released.

We can maybe just line-up the actual Content CLI release creation to be after the one in Pacman, if we don't want a long living PR.

[Buqeta (Buqeta)]

I would merge this only after the API change is released.

We can maybe just line-up the actual Content CLI release creation to be after the one in Pacman, if we don't want a long living PR.

Sure, we can do that too. I'll remind the next release manager. I think it's you next week. 😄

[Jeta (jetakasabaqi)]

I would merge this only after the API change is released.

We can maybe just line-up the actual Content CLI release creation to be after the one in Pacman, if we don't want a long living PR.

Sure, we can do that too. I'll remind the next release manager. I think it's you next week. 😄

The documentation changes will be live immediately, so that won't work in this case.

[Buqeta (Buqeta)]

I would merge this only after the API change is released.

We can maybe just line-up the actual Content CLI release creation to be after the one in Pacman, if we don't want a long living PR.

Sure, we can do that too. I'll remind the next release manager. I think it's you next week. 😄

The documentation changes will be live immediately, so that won't work in this case.

Oh right, I changed the .md file too. We can leave this PR open until then. It's fine by me.