I personally never knew how to handle this bizarre type, and never
understood why it existed in TOSCA. Since it always can ever have one and
only one value, what's the point of having "required" or "default" for it?
How should those be handled?
I will leave it up to you, or another contributor to
Hi,
I tried using the property type 'null' in one of the properties of a node type.
And I didn't pass any value to the property in the respective node template.
When I tried storing the template, I get the following validation issues,
Storing service template null_test...
Validation issues:
My vote is +1.
--Tom
On Thu, Jan 4, 2018 at 11:35 AM, Maxim Orlov wrote:
>1. Validated signature & checksums
>2. Validated LICENSE, NOTICE, DISCLAIMER, "-incubating" in file name
>3. Ran RAT check
>4. Made a clean install using "pip install ."
>5. Ran tests using "make test
+1
On Thu, Jan 4, 2018 at 10:54 AM, Thomas Nadeau wrote:
> I updated the script and pushed the artifacts again. The issue is that
> test.pypi.org does not let you change artifacts once they've been pushed,
> so I cannot delete the one I pushed to replace it with the updated one.
> This should n
I updated the script and pushed the artifacts again. The issue is that
test.pypi.org does not let you change artifacts once they've been pushed,
so I cannot delete the one I pushed to replace it with the updated one.
This should not be an issue, as you can test/verify everything else and
when I pu
Can you use the one that is checked in ?
https://github.com/apache/incubator-ariatosca/blob/master/release/asf-release.sh#L138
On Thu, Jan 4, 2018 at 11:37 AM Thomas Nadeau wrote:
> The asf-release.sh script we are currently using names them as they are:
>
> function _sign_package {
> local
The asf-release.sh script we are currently using names them as they are:
function _sign_package {
local ARCHIVE_NAME=$1
echo "Signing archive ${ARCHIVE_NAME}..."
gpg --armor --output ${ARCHIVE_NAME}.asc --detach-sig ${ARCHIVE_NAME}
gpg --print-md MD5 ${ARCHIVE_NAME} > ${ARCHIVE_NA
1. Validated signature & checksums
2. Validated LICENSE, NOTICE, DISCLAIMER, "-incubating" in file name
3. Ran RAT check
4. Made a clean install using "pip install ."
5. Ran tests using "make test"
+1
On Thu, Jan 4, 2018 at 5:59 PM Thomas Nadeau wrote:
> Aria Community:
>
> This
Thomas,
The files are still named "sha" instead of "sha512"
John
On Thu, Jan 4, 2018 at 10:59 AM Thomas Nadeau wrote:
> Aria Community:
>
> This is a vote to release Apache AriaTosca (Incubating) 0.2.0. If the vote
> passes, another vote for approving the release will take place on the
> Apach
Aria Community:
This is a vote to release Apache AriaTosca (Incubating) 0.2.0. If the vote
passes, another vote for approving the release will take place on the
Apache Incubator's PMC. Please verify the various release artifacts and
respond to the list with your results. Instructions for locating
I just wanted to let everyone know that I've now figured out the process,
and gotten a bunch of related stuff sorted (i.e.: pypi access), and so we
are now ready to re-start the review candidate voting process. Artifacts
are signed, and in place at Apache's dist area as well as at pypi tests
area.
Hi,
We see that "type" is optional in Input Definition (under Topology Template) as
per TOSCA SPEC 1.0 latest but in latest ARIA it has become mandatory.
>From code perspective, it is because of the below change
Old: templates.py
@object_dict_field(ParameterDefinition) # Where ParameterDefin
Well, the question is can we achieve the same functionality via the
initiator to the model storage. Although it is initiated only once, using
the sessionfactory with the initiator might help.
If not, it could be a great contribution to the project.
On Wed, Jan 3, 2018 at 7:50 AM D Jayachandran
wr
13 matches
Mail list logo