Project field not returning properly in workspace

[anoonan-zz]

python-tfe version

0.1.0

Description

When accessing a workspace, the workspace object contains a project_id attribute, but that attribute is set to None even though the workspace itself is assigned to a project. This seems to be because the workspace _ws_from() function uses:

    proj_id: str | None = None
    proj = attr.get("project")
    if isinstance(proj, dict):
        proj_id = proj.get("id") if isinstance(proj.get("id"), str) else None

to get the project ID. Unfortunately, the project_id, at least in TFE 1.0 and, to my knowledge, earlier versions, is not stored in the attributes section, but in the relationships section (.data.relationships.project.data.id)

Testing plan

1. use workspace.show() to gather a workspace object.
2. print the project_id for the workspace

Expected Behavior

The project ID is printed

Actual Behavior

is ID is shown as "None"

Additional Context

Running TFE 1.0.0 right now

[isivaselvan]

@anoonan-zz Thank you for reporting this! The necessary updates on the workspace object related to relationship have been scheduled for the upcoming release.

[anoonan-zz]

You used this phrasing in the other ticket as well. Could you confirm what this statement means? Are you saying, "Yes, I confirm that this is a bug and we are scheduling this for the next release, but it's not fixed in the release branch yet" or "Yes, I confirm this is a bug and it is already fixed in the release branch, we are just waiting for the release to fix this issue"?

I ask because when I look at next-0.1.1, it's not fixed, so it's not clear if your expectation is that it is fixed.

[anoonan-zz]

Random side-comment: I noticed that the next-0.1.1 branch has the introduction of the teams resources (yay!), but at least right now the version CHANGELOG implies "0.1.1" (plus the branch name, etc). But these are feature introductions as opposed to minor patches to fix bugs in existing features... Shouldn't the version be 0.2.0 or something similar if you are using semver (or some reasonable approximation of semver)?

[iam404]

@anoonan-zz these resources was suppose to be released under 0.1.0 but wasn't able to rollout due to tests issues, hence updated code are getting merged in the minor release. For now our roadmap for 0.2.0 include stacks, registry and others bug fixes.