Document manifest property dependencies.<item>.namespace

[andreafalzetti]

As per the title!

See: https://github.com/okteto/okteto/blob/master/pkg/model/manifest.go#L1002

[aroramrinaal]

hey @andreafalzetti ,
I would like to work on this good-first-issue.

[andreafalzetti]

Thanks for the interest @aroramrinaal - feel free to start on this. If you need support, don't hesitate to reach out :)

[ArslanYM]

Is this issue still open?

[andreafalzetti]

@ArslanYM yes, it is

[ArslanYM]

Can I work on this?

[andreafalzetti]

@ArslanYM thanks for offering your help, the docs repo is this one: https://github.com/okteto/docs

if you need any context or help, let me know

thanks!

[ArslanYM]

Can you give some context about the issue and how to approach this?

[andreafalzetti]

Can you give some context about the issue and how to approach this?

This is a docs issue, so it would require understanding what property we're documenting here. The namespace of a dependency allows deploying a dependency in a different namespace. It's not the most common scenario but it's a use case that exists. At the moment namespace is not mentioned in docs: https://www.okteto.com/docs/reference/manifest/#dependencies-string-optional

As part of this ticket we can add it to the docs

[UtkarshUmre]

Is this issue still open?

[seanson]

Definitely still an issue as the Manifest documentation still gives the type as an optional list of strings and there are quite a few properties available but only documented above as an "extended notation".

https://github.com/okteto/okteto/blob/18ce425b3e1a51da6a345c38dc391ac1fd21fd16/pkg/deps/deps.go#L31

[seanson]

Apologies, as a followup: It looks like Namespace itself is going to be removed in the upcoming 3.x branch, but still exists in the 2.31.0 release. I think it would still be worth documenting as part of the whole resource though.