I would like to sync repository contents from GitLab, similar to the existing GitHub functionality.

On the credential pages, I would like to see which Vessels are actively using the credentials so that I can have more confidence which Vessels are going to be impacted by me removing or updating a credential group.

I would like to be able to see the entire output of a log (that I can see in the UI) within the CSV that the API exports. This would be helpful for extracting information like the variables used, IDs synced, etc.

I would like the ability to set Environment Variables at the Fleet level. This way, I could set a variable like $FILE_NAME and use it as an input on every Vessel. If I wanted to change the file name, I would only have to update it in one location.

I would like to be able to set custom Environment Variables when setting up a Blueprint Vessel. The biggest use case is running DML queries for Snowflake/Redshift where I might want to UNLOAD data to another service. I have to provide credentials in my SQL, which gets shown in the logs. I would prefer to reference an environment variable in the SQL... but I can't set that environment variable right now.

I would like to get insight into the quality of data my data pipeline is processing. Something like logging metadata about file names created, sizes, rows/columns, etc. I think this could be useful to track down potential issues.

I would like the ability to write and save notes about my Fleets and Vessels. This would help me explain to my team what they do and how to troubleshoot them if something goes wrong.

I would like to have 2FA on my account for additional security measures. This would make me feel better about an outside party not having the ability to gain access to my account.

As an admin, I should be able to set an option that allows myself, or another user, to access all future created projects, rather than needing to continuously give myself access to new projects.

Currently, I can stop a running Vessel (which ends up stopping the Fleet). However, it would be useful to have a button at the Fleet log level to stop the entire Fleet from continuing to run.