Skip to main content
Question

Extracting workspace metadata

  • September 12, 2024
  • 3 replies
  • 39 views

_jacques_
Supporter
Forum|alt.badge.img+14

Hi, 

 

I’m working on automating our FME workspace deployment on Azure Devops using the functionality in pipelines. One thing I would like to automate is to extract metadata about every workspace pushed to the repository and write it to a README.md file. With such a file placed next to every workspace it would be easier to navigate our repo. I would like to see basic information like workspace name, description, number of transformers etc.

What’s the best way to extract this data? I have tried using python to read the .fmw text directly and using the FME workspace reader with partial success. 

 

Has anyone else done something similar or have ideas? 

3 replies

redgeographics
Celebrity
Forum|alt.badge.img+49

My suggestion would be to use the workspace reader. You say you’ve got “partial success”, can you elaborate on that? What would you like to read that you can’t find? 


_jacques_
Supporter
Forum|alt.badge.img+14
  • Author
  • Supporter
  • September 12, 2024
redgeographics wrote:

My suggestion would be to use the workspace reader. You say you’ve got “partial success”, can you elaborate on that? What would you like to read that you can’t find? 

 

For some reason I could not extract the workspace description when using a workspace reader in FME Forms 2024.1. But the main problem was setting up FME on the virtual machine on Azure. Using python to read the workspace as an xml file seems like the best option so far.


redgeographics
Celebrity
Forum|alt.badge.img+49

The WorkspaceProperties feature type contains one feature per workspace with attributes containing, amongst others, the workspace description, help and history. The description and help are HTML formatted though so if you just want to extract the value it’ll be a bit more work.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings