python-tfe version
Description
When using the Workspace object, several relationships and information is missing compared to the TFE API. The specific fields that we noticed and currently care about are:
latest-run : different from current-run, latest-run is the last run regardless of it being applied/errored
latest-change-at : datetime of the latest change, different from "updated-at"
last-assessment-result-at : datetime of the last assessment run
source-module-id : ID of module used for no-code workspace
Given some of the other tickets, the preference would be parity with current TFC/TFE output rather than opening tickets for these fields individually.
Testing plan
1. Create a no-code workspace.
2. Perform a few applies.
3. curl the workspace object from the API. Note that these fields exist in the API.
4. Load the workspace object and attempt to read these fields.
Expected Behavior
The attributes should return data (in the case of latest-run, a Run object, for source-module-id, a RegistryModule object or module ID -- may need to be ID, latest TFE release mentions deletion of module in registry without deleting workspaces, not sure how that looks in the API).
Actual Behavior
Errors because the fields don't exist.
Additional Context
python-tfe version
Description
When using the Workspace object, several relationships and information is missing compared to the TFE API. The specific fields that we noticed and currently care about are:
latest-run : different from current-run, latest-run is the last run regardless of it being applied/errored
latest-change-at : datetime of the latest change, different from "updated-at"
last-assessment-result-at : datetime of the last assessment run
source-module-id : ID of module used for no-code workspace
Given some of the other tickets, the preference would be parity with current TFC/TFE output rather than opening tickets for these fields individually.
Testing plan
Expected Behavior
The attributes should return data (in the case of latest-run, a Run object, for source-module-id, a RegistryModule object or module ID -- may need to be ID, latest TFE release mentions deletion of module in registry without deleting workspaces, not sure how that looks in the API).
Actual Behavior
Errors because the fields don't exist.
Additional Context