[Azure Blob Storage] When does version 2.1.2 become Published?
Question
azure-blob-storage
Web icon
Forge component by Barduino

Hi,

We would like to enable our users to download files with a SAS key. I noticed that version 2.1.2. has support for this (based on the release notes). This version is currently under development and we have a policy that prohibits us from using "under development" components. Is there an ETA on when this component becomes published? 

Best,

Vincent


Hi,

Is there any change that this component will be updated or is it not maintained anymore? Knowing the latter is also useful so we can seek alternatives.

Kind regards,

Vincent 

Vincent Koning wrote:

Hi,

Is there any change that this component will be updated or is it not maintained anymore? Knowing the latter is also useful so we can seek alternatives.

Kind regards,

Vincent 


Hi Vincent,


I'm a true believer in the open source movement. 

Would you like to join the team and submit the changes you are looking for?


Cheers

Hi Barduino,

I would like to join the team. I have some other things I would like to add so that could be a nice starting point when I get some time available in a month or 2. 

Note that the changes that I currently need are already available, just in a "under development" state. A quick change to "released" would be enough for me at the moment :)


Kind regards,

Vincent

Vincent Koning wrote:

...

Note that the changes that I currently need are already available, just in a "under development" state. A quick change to "released" would be enough for me at the moment :)

Can you help me understand why?


Sure. My company has a policy that anything "under development" can't be used in our applications. It prevents us from using software where the makers themselves don't find the component stable enough to use and should therefor increase stability of our own applications. It's a policy thing and I can't change anything about it.

Vincent Koning wrote:

Sure. My company has a policy that anything "under development" can't be used in our applications. It prevents us from using software where the makers themselves don't find the component stable enough to use and should therefor increase stability of our own applications. It's a policy thing and I can't change anything about it.

Got it, thanks.

Looks like you've been through the code, while I haven't, how about I invite you to the team and you submit a new stable version?

Would that work for you?

Note that once you submit a new version it will most likely stop being considered trusted until it is reviewed again.



Barduino wrote:

Note that once you submit a new version it will most likely stop being considered trusted until it is reviewed again.

How does one review other forge components anyway? 


Vincent Koning wrote:


How does one review other forge components anyway? 


Hi Vincent,

On the component main page, switch to the review tab, there is a write a review button.

However I think folks who are on the team can not review their own components, I can't review this one...

Cheers


Hi everyone,

I went in and added the missing description on those 2 new methods and released a new stable version.

Regards,

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.